Telecommunications soft client having a gui-less operating mode

ABSTRACT

The technology disclosed herein enables narration of occurrences in a telecommunications soft client operating in a GUI-less mode. In a particular embodiment, a method includes, in a user system, operating the telecommunications soft client in a first mode. In the first mode, the user system does not present a GUI to a user for the telecommunications soft client. A screen reader application is also executing on the user system. While in the first mode, the method includes audibly describing a first occurrence for the telecommunications soft client and receiving global user input into the telecommunications soft client. The screen reader application describes a second occurrence for a first application executing, and displaying an application window, on the user system.

RELATED APPLICATIONS

This application is related to and claims priority to U.S. ProvisionalPatent Application 62/985,618, titled “TELECOMMUNICATIONS SOFT CLIENTTHAT DOES NOT INTERFERE WITH A SCREEN READER APPLICATION,” filed Mar. 5,2020, and which is hereby incorporated by reference in its entirety.

TECHNICAL BACKGROUND

Software applications exist that allow personal computers to be used asreal-time telecommunication endpoints (commonly referred to as “softclients”). Examples include Skype, Cisco Jabber and Avaya IX Workplace.All of these soft clients present information, such as CallerIdentification and whether a call is on hold, visually on a displayusing a graphical user interface (GUI). Blind users of personalcomputers utilize specialized text-to-speech screen-reading software inorder to access visually presented information. By far, the mostcommonly used screen reader is a product called JAWS (Job Access WithSpeech), although other screen readers exist.

Although many telecommunications soft clients are compatible with thescreen reader, there is a usability problem with this configuration. Thescreen reader, as implied by the its name, is a screen-readingapplication and its text-to-speech functionality is limited to thewindow that has focus. As a result, a blind person who wants to use anapp on their client (e.g., monitoring events that are changing in areal-time spreadsheet) at the same time they are engaging in complextelephony operations must necessarily change focus back and forth, andmay miss information that is presented by the app that does not havefocus. (Sighted people do not have this problem because windows thatdon't have focus can still be visible.)

SUMMARY

The technology disclosed herein enables narration of occurrences in atelecommunications soft client operating in a GUI-less mode. In aparticular embodiment, a method includes, in a user system, operatingthe telecommunications soft client in a first mode.

In the first mode, the user system does not present a GUI to a user forthe telecommunications soft client. A screen reader application is alsoexecuting on the user system. While in the first mode, the methodincludes audibly describing a first occurrence for thetelecommunications soft client and receiving global user input into thetelecommunications soft client. The phrases “global user input” and“global command” apply to inputs and commands that elicit a responsefrom the telecommunications soft client regardless of whether thetelecommunications soft client, or another application window, hasfocus. The screen reader application describes a second occurrence for afirst application executing, and displaying an application window, onthe user system.

In some embodiments, the method includes operating thetelecommunications soft client in the first mode in response todetermining that the screen reader application is executing on the usersystem.

In some embodiments, the method includes operating thetelecommunications soft client in the first mode in response to inputfrom the user selecting the first mode over at least a second mode thatpresents the GUI for the telecommunications soft client.

In some embodiments, the global user input comprises an instruction inan instruction group comprising a call answer instruction, a call muteinstruction, a call hold instruction, and a call initiation instruction.

In some embodiments, audibly describing the first occurrence comprisesgenerating speech that conveys the first occurrence to the user.

In some embodiments, the first occurrence comprises an event in an eventgroup comprising an incoming call request, a new voicemail notification,and a feature status notification.

In some embodiments, the application window is a current focus window onthe user system.

In some embodiments, audibly describing the first occurrence uses afirst speaker of the user system and the screen reader applicationdescribes the second occurrence using a second speaker of the usersystem.

In some embodiments, audibly describing the first occurrence uses afirst voice and the screen reader application describes the secondoccurrence using a second voice.

In some embodiments, the global user input comprises a key combinationinput into a user interface of the user system that is mapped to thetelecommunications soft client.

In another embodiment, an apparatus is provided having one or morecomputer readable storage media and a processing system operativelycoupled with the one or more computer readable storage media. Programinstructions stored on the one or more computer readable storage media,when read and executed by the processing system, direct the processingsystem to operate the telecommunications soft client in a first mode. Inthe first mode, the user system does not present a GUI to a user for thetelecommunications soft client. A screen reader application is alsoexecuting on the user system. While in the first mode, the programinstructions direct the processing system to audibly describe a firstoccurrence for the telecommunications soft client and receive globaluser input into the telecommunications soft client. The screen readerapplication describes a second occurrence for a first applicationexecuting, and displaying an application window, on the user system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an implementation for operating a telecommunicationssoft client in a GUI-less mode.

FIG. 2 illustrates an operational scenario wherein a telecommunicationssoft client operates in a GUI-less mode.

FIG. 3 illustrates a desktop wherein a telecommunications soft clientoperates in a GUI-less mode.

FIG. 4 illustrates an implementation for operating a telecommunicationssoft client in a GUI-less mode.

FIG. 5 illustrates an operational scenario wherein a telecommunicationssoft client operates in a GUI-less mode.

FIG. 6 illustrates an operational scenario wherein a telecommunicationssoft client operates in a GUI-less mode.

FIG. 7 illustrates a computing architecture for operating atelecommunications soft client in a GUI-less mode.

DETAILED DESCRIPTION

The telecommunications soft client described herein address shortcomingsof screen reader software, especially with regard to users who areblind, by providing audible notifications of telephony events (e.g.,Caller ID, whether a call is on hold, receipt of new voicemail) via amechanism that is independent of, and does not interfere with, screenreader software also executing on a user system. The lack ofinterference with the screen reader software, including an ability touse the screen reader with a visible application that has focus whileconcurrently using the soft client for telephony operations, is achievedby providing a soft client mode in which there is no GUI. Specifically,because the soft client has no GUI, there is no ability to capturefocus, nor is there a need for focus in order to provide voicenotifications of telephony events, thereby leaving the screen readerfree to support applications with GUI's, which the screen readerrequires to be the focus window to provide accessibility to blind users(or other users who find the screen reader beneficial).

FIG. 1 illustrates implementation 100 for operating a telecommunicationssoft client in a GUI-less mode. Implementation 100 includes user system101 and communication network 102. User system 101 and communicationnetwork 102 communication over communication link 111. Communicationlink 111 may be wired and/or wireless. Communication link 111 is shownas a direct link but may include intervening systems, networks, and/ordevices. User system 101 may be a telephone, laptop, personal computer,tablet computer, or some other type of user operable computing system.Communication network 102 includes one or more networks, such as acircuit switched telephone network, local area packet network, wide areanetwork (e.g., the Internet), or some other type of network over whichtelecommunications may be carried—including combinations thereof.

In operation, user system 101 executes telecommunications soft client121, screen reader application 122, and application 123. User 141operates user system 101, in part, by interacting with user interfacesof telecommunications soft client 121, screen reader application 122,and application 123. Telecommunications soft client 121 allows user 141to telecommunicate with one or more other users, via their respectiveuser systems, over communication network 102. The other user systems mayalso execute a telecommunications soft client like telecommunicationssoft client 121 or may communicate over communication network 102 insome other manner (e.g., may be a circuit switched telephone).Telecommunications between user system 101 and the one or more otheruser systems may be communication sessions over which voice, video,text, or some other type of user communications are exchanged—includingcombinations thereof.

User system 101 also executes application 123. Application 123 is anytype of application having a GUI with which user 141 may interact.Application 123 may be an office productivity application (e.g., wordprocessing, spreadsheet, etc.), an email client, a service ticketingapplication, a web browser, or any other type of application executableby user system 101. User system 101 further executes screen readerapplication 122. Screen reader application 122 is an application thatassists users by providing audible information to user 141 (e.g.,through one or more speakers of user system 101). Screen readerapplication 122 may simply perform text-to-speech conversion of words ona display of user system 101 or may provide additional information aboutwhat is being displayed (e.g., information about events that occur in anapplication or an operating system of user system 101, information abouticons being displayed, information about menu options being displayed,etc.). Essentially, the information provided by screen readerapplication 122 allows user 141 to operate user system 101 (e.g.,interact with the applications and/or operating system thereon) withoutnecessarily being able to view a display of user system 101, as may bethe case if user 141 is visually impaired. Screen reader application 122may require that a window for an application be the current focus window(e.g., the window that is at the forefront on a desktop being displayedby user system 101) in order to provide screen reading functionality tothe application, as opposed to operating on other applications (havingwindows or otherwise) or the operating system of user system 101. Inthose cases, screen reader application 122 will provide informationabout the focus-window application, while not providing informationabout other applications.

FIG. 2 illustrates operational scenario 200 wherein a telecommunicationssoft client operates in a GUI-less mode. In operational scenario 200,telecommunications soft client 121 is operating on user system 101 inGUI-less mode 131 (201). When operating in GUI-less mode 131, usersystem 101 does not present a GUI to user 141 for telecommunicationssoft client 121. User system 101 does not present a GUI fortelecommunications soft client 121 because telecommunications softclient 121 has no GUI in GUI-less mode 131. As such, there is no GUIand, consequently, no application window for user system 101 to present.Telecommunications soft client 121 may have multiple operating modes ormay have only GUI-less mode 131. For example, telecommunications softclient 121 may include at least one operating mode, other than GUI-lessmode 131, that has a GUI of some type.

When telecommunications soft client 121 is operating in GUI-less mode131 while executing on user system 101, telecommunications soft client121 audibly describes an occurrence for telecommunications soft client121 (202). The occurrence may be an event that happens intelecommunications soft client 121, may be a notification generated bytelecommunications soft client 121, may be information that would bedisplayed had telecommunications soft client 121 been operating in amode that had a GUI, may be status information, or may be some othertype of information that would be useful to user 141's use oftelecommunications soft client 121. The occurrence may include anincoming call, a caller's identity (e.g., caller ID), receipt of a newvoice message, a status update that new voice messages available, astatus update that no new voice messages, a call disconnecting, anotherparty leaving a communication session, call forwarding being turnedon/off, call forwarding status, or some other type of occurrencerelevant to telecommunications. As should be gleaned from the aboveexamples, the occurrence may be an event that happens in real-time, maybe a status update describing a current state of telecommunications softclient 121, or may be some other information related to the operation oftelecommunications soft client 121. In some examples, the occurrence mayhappen at the request of user 141 (e.g., user 141 may request a statusupdate). Similarly, rather than having to explicitly request a statusupdate each time user 141 desires a description of a status updateoccurrence, user 141 may be able to define when particular status updateitems should be described (e.g., once every hour or upon a changehappening). To audibly describe the occurrence, telecommunications softclient 121 directs user system 101 to produce sound that describes theoccurrences. The sound may be voice (e.g., a synthetically generatedvoice or prerecorded voice) that explicitly describes the occurrence inwords (e.g., a voice that says “you have an incoming call from Paul”) ormay be another type of sound (e.g., tone, tone pattern, etc.) that user141 associates with a corresponding occurrence.

In this example, telecommunications soft client 121 also receives globaluser input from user 141 (203). Since telecommunications soft client 121is operating in GUI-less mode 131, there is no GUI into which user 141can provide input to telecommunications soft client 121 (e.g., input toanswer an incoming communication session request or request playback ofa voicemail). Global user input is user input that an operating systemdirects to a corresponding application regardless of whether thatapplication is currently the focus. Global user input may include apattern of keystrokes into a keyboard, mouse/trackpad gestures,touchscreen gestures, audible voice commands, or some other type ofinput. In some examples, certain user input (e.g., key combination) mayindicate telecommunications soft client 121 while input receivedsubsequent to that particular input corresponds to a particularinstruction to telecommunications soft client 121. For instance, user141 may press the control key and the space bar at the same time tonotify user system 101 that the following user input should be directedto telecommunications soft client 121. In other examples, inputcorresponding to a particular instruction to telecommunications softclient 121 does not require that input indicating telecommunicationssoft client 121 first be received. The instructions totelecommunications soft client 121 may include instructions that directtelecommunications soft client 121 to take actions that includeaccepting an incoming communication session request, initiating acommunication session, ending a communication session, ignoring acommunication session request, holding/un-holding a call,muting/un-muting a call, stopping the audible description of anoccurrence, redialing, transferring a call, selecting a contact,selecting a message, or any other type of action that may occur within atelecommunications soft client. The global user input may be defined bya user, such as user 141, by telecommunications soft client 121, or bysome other entity.

While telecommunications soft client 121 is handling the description ofoccurrences in telecommunications soft client 121, screen readerapplication 122 is able to describe occurrences for application 123,which does display a GUI with which user 141 can interact (204). Theoccurrences could be any type of event or information available inapplication 123 depending on the type of application. For example,application 123 may be a spreadsheet application and the occurrencecould be user 141 selecting cells in a spreadsheet. Screen readerapplication 122 may generate speech that reads the contents of thoseselected cells aloud to user 141. Since telecommunications soft client121 handles descriptions of occurrences therein, even if screen readerapplication 122 only provides functionality to the application windowhaving focus, user 141 can still hear descriptions of telecommunicationssoft client 121 even when a window of telecommunications soft client 121is not the window currently having focus. User 141 is, therefore, freeto user other applications on user system 101 without worrying that anoccurrence in telecommunications soft client 121 will be missed due to awindow of telecommunications soft client 121 not currently having focus.

It should be understood that, while step 203 is described after step 202in operational scenario 200, it is possible that telecommunications softclient 121 would receive global user input prior to an occurrence thattriggers an audible description by telecommunications soft client 121.In those examples, step 203 would occur before step 202. Of course, step202 and step 203 may repeat any number of times due to additionaloccurrences triggering audible description by telecommunications client121 and additional global user input directed to telecommunicationsclient 121.

FIG. 3 illustrates desktop 300 wherein a telecommunications soft clientoperates in a GUI-less mode. Desktop 300 is an example GUI of anoperating system executing on user system 101 and is displayed by adisplay of user system 101. Desktop 300 includes application window 301,which is currently the focus window, and application windows 302 and303, which are not currently the focus window. Application window 301may be the focus because a user of desktop 300 may have more recentlyselected application window 301 (e.g., clicked within application window301), application window 301 may be most recently launched, or someother manner in which user 141 may indicate that application window 301should be the focus of their attention on desktop 300. Applicationwindow 301 is a window of application 123. Application windows 302 and303 may also be application windows of application 123 or may beapplication windows of one or more other applications executing on usersystem 101.

By virtue of application window 301 being the focus application window,screen reader application 122 will audibly describe to user 141 thecontents of and/or events occurring within application window 301 (e.g.,will use a speaker of user system to output audio, such as a synthesizedvoice or event specific tones, describing application window 301). Inthis example, while application window 301 is the focus window, screenreader application 122 does not audibly describe anything withinapplication window 302 or application window 303. Should the focuswindow switch from application window 301 to one of application window302 or application window 303, then screen reader application 122 wouldalso switch to audibly describing to user 141 the contents and/or eventsoccurring within the new focus window and not application window 301. Assuch, a user who is unable to see what is happening in a window that isnot the focus (e.g., a blind user), may miss events that occur in anon-focus window because screen reader application 122 will not reportthose events.

In this example, telecommunications soft client 121 is operating inGUI-less mode 131. Soft client icon 311 is located in the menu bar toshow that telecommunications soft client 121 is executing but does notpresent a GUI for controlling telecommunications soft client 121. Inother examples, there may be no visual indicator on desktop 300 thattelecommunications soft client 121 is executing. Similarly, though notshown in this example, desktop 300 may present a visual indicator thatscreen reader application 122 is running. In some examples,telecommunications soft client 121 may detect when screen readerapplication 122 is in use and automatically switch to a non-GUI mode iftelecommunications soft client 121 also has a GUI mode. Whentelecommunications soft client 121 is in GUI-less mode 131, user 141 mayinteract with telecommunications soft client 121 via commands receivedin global user input (e.g., voice input, keyboard input, etc.) withinthe operating system of user system 101. These global commandsautomatically apply to telecommunications soft client 121 even ifanother application window is in focus. The global commands may be usedto initiate a communication session, end a communication session, muteuser system 101's microphone, add participants to a session, or performsome other action that may otherwise be performed if telecommunicationssoft client 121 was presenting a user interface.

Since telecommunications soft client 121 does not have a GUI window,screen reader application 122 cannot describe the occurrences (e.g.,events, contents, statuses, etc.) within that non-existent window.Advantageously, screen reader application 122 will never operate on awindow for telecommunications soft client 121 and miss describingoccurrences in another window that occur when telecommunications softclient 121's window is the focus. Telecommunications soft client 121instead includes its own narrator functionality that audibly describesto user 141 events occurring with respect to telecommunications softclient 121 (e.g., identifying new participants joining/leaving acommunication session, indicating that a communication session is beingestablished, indicating how long a session has been running, indicatinga line status, etc.). The narrator functionality as a whole may beincluded in telecommunications soft client 121 (e.g., telecommunicationssoft client 121 itself provides audio output information to thespeakers, headset, or other audio device, of user system 101) ortelecommunications soft client 121 may leverage other applicationsand/or the operating system of user system 101 (e.g., telecommunicationssoft client 121 indicates to another application or the operating systemwhat is occurring in telecommunications soft client 121 and the otherapplication or operating system generates and provides the audio outputinformation to the speakers, headset, or other audio device, of usersystem 101).

When using telecommunications soft client 121 in GUI-less mode 131described above, user 141 is able to interact with telecommunicationssoft client 121 and be provided with audio descriptions of occurrenceswith respect to telecommunications soft client 121 (e.g., to participatein a conference call) while not needing to take another applicationwindow, such as application window 301, out of focus. Screen readerapplication 122 can, therefore, describe application window 301 (or anyother window that becomes the focus) while telecommunications softclient 121's own mechanisms describe the events occurring with respectto telecommunications soft client 121. In some examples,telecommunications soft client 121's audio output may be configured suchthat the voice (synthesized, prerecorded, or otherwise) used bytelecommunications soft client 121 is different than the voice used byscreen reader application 122 (e.g., a male voice may be used by screenreader application 122 while telecommunications soft client 121 may usea female voice). The different voices will allow user 141 to more easilydistinguish between descriptions provided by screen reader application122 and telecommunications soft client 121.

FIG. 4 illustrates implementation 400 for operating a telecommunicationssoft client in a GUI-less mode. Implementation 400 includes display 401,speaker 402, and speaker 403. Display 401 is a display of user system101 in this example. While shown separately, speaker 402 and speaker 403may be incorporated into display 401 or some other component of usersystem 101 (e.g., into the palm rest assembly of user system 101 if usersystem 101 is a laptop). As discussed above, different voices may beused to differentiate between descriptions from telecommunications softclient 121 and screen reader application 122. In this example, audiooutput from screen reader application 122 may be directed throughspeaker 402 while audio output from the narration functionality oftelecommunications soft client 121 may be directed through speaker 403.User 141 should then more easily be able to differentiate whether adescription is coming from telecommunications soft client 121 or screenreader application 122 based on from which speaker of speakers 402 and403 that user 141. Using the two different speakers in this manner maybe the only manner in which descriptions from telecommunications softclient 121 and screen reader application 122 are differentiated or maybe used in conjunction with other types of differentiators, such as thedifferent voices described above.

While implementation 400 includes two speakers, other types of audiooutput components may be used in other examples. For example, user 141may wear a headset connected to user system 101. Audio from screenreader application 122 may use the headset to present descriptions touser 141 while audio from telecommunications soft client 121 may use aninternal speaker of user system 101.

FIG. 5 illustrates operational scenario 500 wherein a telecommunicationssoft client operates in a GUI-less mode. Operational scenario 500 is anexample of implementations 100, 300, and 400. While softwareapplications (i.e., telecommunications soft client 121, application 123,and screen reader application 122) are described as performing varioussteps of operational scenario 500, it should be understood that thesteps are performed by user system 101 at the direction of therespective applications. In operational scenario 500, telecommunicationssoft client 121 automatically determines that screen reader application122 is executing and enabled (i.e., active to describe occurrences) onuser system 101 at step 1. Telecommunications soft client 121 maycommunicate with screen reader application 122 to determine that screenreader application 122 is enabled or may communicate with an operatingsystem of user system 101 to determine that screen reader application122 is enabled. For instance, a component of the operating system may beaccessed (e.g., through an Application Programing Interface) todetermine whether any accessibility applications, such as screen readerapplication 122, are enabled on user system 101.

Upon determining that screen reader application 122 is enabled,telecommunications soft client 121 operates in GUI-less mode 131 at step2. Telecommunications soft client 121 may have previously been operatingin a mode with a GUI prior to determining that screen reader application122 is enabled and automatically switches to GUI-less mode 131 duringstep 2. Alternatively, steps 1 and 2 may be performed upon starting theexecution of telecommunications soft client 121 and, as such, GUI-lessmode 131 becomes the initial operating mode for telecommunications softclient 121 upon opening. When GUI-less mode 131 is enabled fortelecommunications soft client 121, telecommunications soft client 121narrates information about its own operation (e.g., occurrences therein)and does not present a GUI to avoid interfering with screen readerapplication 122's narration of other applications.

In this example, event 501 occurs within telecommunications soft client121. Event 501 may be an incoming communication session request, a newmessage arrival, or any other type of event that may happen in atelecommunications soft client. Responsive to the occurrence of event501, telecommunications soft client 121 generates voice 502, whichdescribes event 501. For example, the voice may say, “event 501 hasoccurred”. Voice 502 may be synthesized, may be a prerecorded message(e.g., telecommunications soft client 121 may select a prerecordedmessage, from many prerecorded messages available to telecommunicationssoft client 121, that corresponds to event 501), may be a combination ofprerecorded words or phrases (e.g., telecommunications soft client 121may piece together a message of voice 502), or may generate voice 502 insome other manner. At this point, voice 502 is a digitizedrepresentation of the sound of voice 502 (e.g., a digitized waveform).In some examples, telecommunications soft client 121 may employ one ormore components of the operating system of user system 101 to generatevoice 502. For instance, the operating system may include atext-to-speech accessibility feature that telecommunications soft client121 directs to generate voice 502.

Once voice 502 is generated, telecommunications soft client 121 sendsvoice 502 at step 5 to speaker 402 so that speaker 402 can play voice502 at step 6. A component of the operating system of user system 101(e.g., an audio device driver or the above-mentioned accessibilityfeature) may be accessed by telecommunications soft client 121 to enabletelecommunications soft client 121 to output sound through speaker 402.In one example, telecommunications soft client 121 may explicitlyinstruct the operating system to play voice 502 through speaker 402. Inanother example, telecommunications soft client 121 voice 502 may begenerated to only use the left stereo channel, which would not produceany sound out of the right stereo channel (i.e., speaker 403).

In this example, a voice (i.e., voice 502) is used to audibly describeevent 501. In other examples, as mentioned above, a tone, pattern oftones, or some other non-voice audio may be used. For instance, aspecific tone frequency/duration corresponding to event 501 may begenerated by telecommunications soft client 121. Likewise, in someexamples, GUI-less mode 131 may include different audio output modes,such as one mode that describes occurrences using voice and another modethat uses non-voice sounds (e.g., tones). Those audio output modes maybe user selectable (e.g., using global user input) or may switchautomatically upon a condition(s) being met. For instance, a voiceoutput mode may be used when telecommunications soft client 121 is notconnected to a call and a tone output mode may be used whentelecommunications soft client 121 is connected to a call.

While telecommunications soft client 121 is operating in GUI-less mode131, event 503 occurs step 7 in application 123. In this example, screenreader application 122 is configured to describe occurrences in anapplication window that is currently the focus window on user system101. Since application 123 is currently the focus window 301 on desktop300 of user system 101, screen reader application 122 detects event 503at step 8. Screen reader application 122 may detect event 503 byperforming image analysis on window 301, may communicate withapplication 123, the operating system, or some other software componentof user system 101, to receive an indication that event 503 occurred, ormay detect event 503 in some other manner. Screen reader application 122generates voice 504 at step 9 in a manner similar to those discussedabove with respect to the generation of voice 502. Once voice 504 isgenerated, screen reader application 122 sends voice 504 to speaker 403at step 10 and speaker 403 plays voice 504 at step 11. Screen readerapplication 122 may send voice 504 in a manner similar to that discussedabove when telecommunications soft client 121 sent voice 502 to speaker402.

Advantageously, user 141 hears voice 502 from speaker 402 and voice 504from speaker 403. Hearing voices 502 and 504 from different locations(i.e., from the locations of speakers 402 and 403) helps user 141differentiate from which narrator a description originated. Descriptionsfrom telecommunications soft client 121 would be heard from speaker 402and descriptions from screen reader application 122 would be heard fromspeaker 403. Further differentiations may also be used to aid user 141,such as using a female voice for telecommunications soft client 121 anda male voice for screen reader application 122.

FIG. 6 illustrates operational scenario 600 wherein a telecommunicationssoft client operates in a GUI-less mode. Operational scenario 600 is anexample of implementations 100, 300, and 400. In particular, operationalscenario 600 is an example of how user input is handled whentelecommunications soft client 121 is operating in GUI-less mode 131.Operational scenario 600 begins with telecommunications soft client 121as the focus window on user system 101 at step 1. In order to be thefocus window, telecommunications soft client 121 is operating in a modethat includes a GUI for the window. User 141 provides mode select input601 at step 2 into user system 101. Mode select input 601 is aninstruction from user 141 for telecommunications soft client 121 tooperate in GUI-less mode 131. Mode select input 601 may be mouse pointeror touchscreen input into the window of telecommunications soft client121, voice command, keyboard input while telecommunications soft client121 is in focus, or some other type of input that an application canreceive when in focus. Upon receiving mode select input 601, user system101 (or an operating system thereof) determines that mode select input601 is not global input directed to a specific application (e.g.,determines that mode select input 601 does not match criteria definedfor any global input) and, therefore, determines at step 3 that, sincetelecommunications soft client 121 is the focus window, mode selectinput 601 should be directed to telecommunications soft client 121. Modeselect input 601 is then provided to telecommunications soft client 121at step 4 accordingly.

Upon receiving mode select input 601, telecommunications soft client 121complies with mode select input 601 and begins operating in GUI-lessmode 131 at step 5. Beginning to operate in GUI-less mode 131 means thatthe GUI window of telecommunications soft client 121 that allowedtelecommunications soft client 121 to be the focus no longer exists onuser system 101. As such, another application window, or a desktop ofuser system 101's operating system, will become the new focus. In thisexample, a window for application 123 becomes the focus (e.g., window301 from desktop 300) at step 6. Subsequent to a window of application123 becoming the focus, user system 101 receives user input 602 fromuser 141. Like mode select input 601, user system 101 (or an operatingsystem thereof) determines that user input 602 is not global inputdirected to a specific application (e.g., determines that user input 602does not match criteria defined for any global input) and, therefore,determines at step 8 that, since application 123 is the focus window,user input 602 should be directed to application 123. User input 602 isthen provided to application 123 at step 9 accordingly.

While telecommunications soft client 121 is operating in GUI-less mode131 and application 123 is the focus window, user system 101 alsoreceives user input 603 at step 10. Upon receiving user input 603, usersystem 101 (or an operating system thereof) determines that user input603 is global user input that maps to telecommunications soft client 121at step 11. User system 101 may store a data structure, such as a table,that includes mappings of global user input (e.g., particular keycombinations, mouse/screen gestures, voice commands, etc.) to particularapplications. In this example, the data structure would indicate thatuser input 603 maps to telecommunications soft client 121. Other mannersof identifying that user input 603 constitutes global user input mayalso be used.

After determining that user input 603 maps to telecommunications softclient 121, user input 603 is passed to telecommunications soft client121 rather than application 123, which is currently the focus window, aswas user input 602. Upon receiving user input 603, telecommunicationssoft client 121 complies with the instruction provided by user input603. For example, user input 603 may be an instruction to initiate acall, to playback voicemail, provide a status update (e.g., a number ofnew messages), or to perform any other action of whichtelecommunications soft client 121 is capable. In a more specificexample, receipt of user input 603 may be event 501 from operationalscenario 500 and may request a status update from telecommunicationssoft client 121. Voice 502 from operational scenario 500 may thenprovide the status update to user 141. Global user input that maps totelecommunications soft client 121 may only map to telecommunicationssoft client 121 when operating in GUI-less mode 131 or may also map totelecommunications soft client 121 when telecommunications soft client121 is operating in a mode with a GUI.

In some examples, mode select input 601 from above may also be globaluser input. Then user 141 can input mode select input 601 even when awindow of telecommunications soft client 121 is not the focus window andstill instruct telecommunications soft client 121 to enter GUI-less mode131. Similarly, a global input command from user 141 may instructtelecommunications soft client 121 operating in GUI-less mode 131 toswitch to a mode with a GUI. Other manners of switchingtelecommunications soft client 121 out of GUI-less mode 131 mayalso/instead be used.

Advantageously, operational scenario 500 and operational scenario 600show that, even though telecommunications soft client 121 does not havea window to be a focus window when operating in GUI-less mode 131, user141 can still receive audible descriptions of telecommunications softclient 121 and can still interact with telecommunications soft client121 through global user input associated with telecommunications softclient 121. Also, since telecommunications soft client 121 does not relyon screen reader application 122 for narration, screen readerapplication 122 can operate on other applications without being affectedby telecommunications soft client 121 ever being the focus window.

FIG. 7 illustrates computing architecture 700 for operating atelecommunications soft client in a GUI-less mode. Computingarchitecture 700 is an example computing architecture for user system101, although user system 101 may use alternative configurations.Computing architecture 700 comprises communication interface 701, userinterface 702, and processing system 703. Processing system 703 islinked to communication interface 701 and user interface 702. Processingsystem 703 includes processing circuitry 705 and memory device 706 thatstores operating software 707.

Communication interface 701 comprises components that communicate overcommunication links, such as network cards, ports, RF transceivers,processing circuitry and software, or some other communication devices.Communication interface 701 may be configured to communicate overmetallic, wireless, or optical links. Communication interface 701 may beconfigured to use TDM, IP, Ethernet, optical networking, wirelessprotocols, communication signaling, or some other communicationformat—including combinations thereof.

User interface 702 comprises components that interact with a user. Userinterface 702 may include a keyboard, display screen, mouse, touch pad,or some other user input/output apparatus. User interface 702 may beomitted in some examples.

Processing circuitry 705 comprises microprocessor and other circuitrythat retrieves and executes operating software 707 from memory device706. Memory device 706 comprises a computer readable storage medium,such as a disk drive, flash drive, data storage circuitry, or some othermemory apparatus. In no examples would a storage medium of memory device706 be considered a propagated signal. Operating software 707 comprisescomputer programs, firmware, or some other form of machine-readableprocessing instructions. Operating software 707 includestelecommunications soft client 708. Operating software 707 may furtherinclude an operating system, utilities, drivers, network interfaces,applications, or some other type of software. When executed byprocessing circuitry 705, operating software 707 directs processingsystem 703 to operate computing architecture 700 as described herein.

In particular, telecommunications soft client 708 directs processingsystem 703 to operating telecommunications soft client 708 in a firstmode. In the first mode, computing architecture 700 does not present aGUI to a user for telecommunications soft client 708. A screen readerapplication is also executing on processing system 703. While in thefirst mode, telecommunications soft client 708 directs processing system703 to audibly describe a first occurrence for the telecommunicationssoft client and receive global user input into the telecommunicationssoft client. The screen reader application describes a second occurrencefor a first application executing, and displaying an application window,on computing architecture 700.

The descriptions and figures included herein depict specificimplementations of the claimed invention(s). For the purpose of teachinginventive principles, some conventional aspects have been simplified oromitted. In addition, some variations from these implementations may beappreciated that fall within the scope of the invention. It may also beappreciated that the features described above can be combined in variousways to form multiple implementations. As a result, the invention is notlimited to the specific implementations described above, but only by theclaims and their equivalents.

What is claimed is:
 1. A method for operating a telecommunications softclient without a graphical user interface (GUI), the method comprising:in a user system, operating the telecommunications soft client in afirst mode, wherein, in the first mode, the user system does not presenta GUI to a user for the telecommunications soft client, and wherein ascreen reader application is executing on the user system; while in thefirst mode: audibly describing a first occurrence for thetelecommunications soft client; receiving global user input into thetelecommunications soft client; and wherein the screen readerapplication describes a second occurrence for a first applicationexecuting, and displaying an application window, on the user system. 2.The method of claim 1, further comprising: operating thetelecommunications soft client in the first mode in response todetermining that the screen reader application is executing on the usersystem.
 3. The method of claim 1, further comprising: operating thetelecommunications soft client in the first mode in response to inputfrom the user selecting the first mode over at least a second mode thatpresents the GUI for the telecommunications soft client.
 4. The methodof claim 1, wherein the global user input comprises an instruction in aninstruction group comprising: a call answer instruction; a call muteinstruction; a call hold instruction; and a call initiation instruction.5. The method of claim 1, wherein audibly describing the firstoccurrence comprises: generating speech that conveys the firstoccurrence to the user.
 6. The method of claim 1, wherein the firstoccurrence comprises an event in an event group comprising: an incomingcall request; a new voicemail notification; and a feature statusnotification.
 7. The method of claim 1, wherein the application windowis a current focus window on the user system.
 8. The method of claim 1,wherein audibly describing the first occurrence uses a first speaker ofthe user system and wherein the screen reader application describes thesecond occurrence using a second speaker of the user system.
 9. Themethod of claim 1, wherein audibly describing the first occurrence usesa first voice and wherein the screen reader application describes thesecond occurrence using a second voice.
 10. The method of claim 1,wherein the global user input comprises a key combination input into auser interface of the user system that is mapped to thetelecommunications soft client.
 11. An apparatus for a user systemexecuting a telecommunications soft client without a graphical userinterface (GUI), the apparatus comprising: one or more computer readablestorage media; a processing system operatively coupled with the one ormore computer readable storage media; and program instructions stored onthe one or more computer readable storage media that, when read andexecuted by the processing system, direct the processing system to:operate the telecommunications soft client in a first mode, wherein, inthe first mode, the user system does not present a GUI to a user for thetelecommunications soft client, and wherein a screen reader applicationis executing on the user system; while in the first mode: audiblydescribe a first occurrence for the telecommunications soft client;receive global user input into the telecommunications soft client; andwherein the screen reader application describes a second occurrence fora first application executing, and displaying an application window, onthe user system.
 12. The apparatus of claim 11, wherein the programinstructions further direct the processing system to: operate thetelecommunications soft client in the first mode in response todetermining that the screen reader application is executing on the usersystem.
 13. The apparatus of claim 11, wherein the program instructionsfurther direct the processing system to: Operate the telecommunicationssoft client in the first mode in response to input from the userselecting the first mode over at least a second mode that presents theGUI for the telecommunications soft client.
 14. The apparatus of claim11, wherein the global user input comprises an instruction in aninstruction group comprising: a call answer instruction; a call muteinstruction; a call hold instruction; and a call initiation instruction.15. The apparatus of claim 11, wherein to audibly describe the firstoccurrence, the program instructions direct the processing system to:generate speech that conveys the first occurrence to the user.
 16. Theapparatus of claim 11, wherein the first occurrence comprises an eventin an event group comprising: an incoming call request; a new voicemailnotification; and a feature status notification.
 17. The apparatus ofclaim 11, wherein the application window is a current focus window onthe user system.
 18. The apparatus of claim 11, wherein a first speakerof the user system is used to audibly describe the first occurrence andwherein the screen reader application uses a second speaker of the usersystem to describe the second occurrence.
 19. The apparatus of claim 11,wherein a first voice is used to audibly describe the first occurrenceand wherein the screen reader application uses a second voice todescribe the second occurrence.
 20. One or more computer readablestorage media having program instructions stored thereon for executing atelecommunications soft client, on a user system, without a graphicaluser interface (GUI), the program instructions, when read and executedby a processing system, direct the processing system to: operate thetelecommunications soft client in a first mode, wherein, in the firstmode, the user system does not present a GUI to a user for thetelecommunications soft client, and wherein a screen reader applicationis executing on the user system; while in the first mode: audiblydescribe a first occurrence for the telecommunications soft client;receive global user input into the telecommunications soft client; andwherein the screen reader application describes a second occurrence fora first application executing, and displaying an application window, onthe user system.